There is no software engineering crisis

There is no software engineering crisis. In order to determine what is meant by the phrase “software engineering crisis,” it is informative to define both the term crisis and the term software engineering. We define crisis to mean a “crucial or decisive point or situation; a turning point.” [1] While not part of the definition, the usual connotation of a crisis further implies an impending disaster as a result doing nothing or making the wrong choices. The IEEE defines software engineering as “the application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software” [3]. When considering the complete phrase “software engineering crisis,” it is also helpful to consider the historical context of the term and its subsequently use. We ask is software engineering really at a turning point? Are there dire consequences if we make the wrong choice on how to proceed? To answer these questions we consider the “software crisis” described in 1968 by NATO. We note that we are not currently in the same “software crisis”, or for that matter, any subsequent crisis. We also debunk the claims that we are in the midst of a perpetual and “chronic software crisis.” by considering the major categories of historical crisis claims. We conclude that the ever-increasing capabilities, ambitions, and expectations placed upon software and software engineers are not signs of a crippling crisis but a natural by-product of healthy exploration and evolution of increasingly improved software.